Conversation
talex5
left a comment
There was a problem hiding this comment.
Great work!
But I think it would be better to keep OCluster as a generic build service (not specific to OCaml or CI stuff), and instead deploy the solver as its own service, connected to its own pool on the scheduler. Allowing this separation was the reason for using AnyPointer and generic jobs, rather than adding a specific solver job type.
|
Ah okay makes sense, thanks for taking a look 👍 I'll pull out the changes to the scheduler and put them on #156 though because at the moment it doesn't actually support custom job submission... (i.e. https://github.com/ocurrent/ocluster/pull/157/files#diff-bb8011a7ab51aad47afd6d179def81780180a05239312e01bb6c75a1e607f8b3) |
|
Closing this PR now in favour of:
Thanks for the quick clarifications :)) |
This PR builds on top of #156 (the first commit) and adds the following:
obuilder. It was also converted from OBuilder to Docker for portability (i.e. so it runs on my mac 🍎)Here is the example pipeline:
And the log at the time of writing for the solver job:
Solver job lob